Disallow unquoted literals in LIKE clause in DESCRIBE statement#154
Merged
Yury-Fridlyand merged 1 commit intointeg-unquoted-percent-in-like-clausefrom Dec 15, 2022
Conversation
LIKE clause
This comment was marked as abuse.
This comment was marked as abuse.
Signed-off-by: Yury-Fridlyand <yuryf@bitquilltech.com>
9eafb4a to
0ec464a
Compare
LIKE clauseLIKE clause
LIKE clauseLIKE clause
forestmvey
reviewed
Nov 9, 2022
|
FYI you spelled |
forestmvey
approved these changes
Nov 9, 2022
forestmvey
left a comment
There was a problem hiding this comment.
Looks good. FYI you spelled unquoted wrong in the branch names.
Author
D'oh, again. I renamed integ branch, the dev one will be deleted after merge. |
GumpacG
reviewed
Nov 14, 2022
| } | ||
|
|
||
| @Test | ||
| public void describe_compatible_with_old_engine_syntax() { |
Author
There was a problem hiding this comment.
Because I made it incompatible
GumpacG
approved these changes
Nov 14, 2022
Author
|
MaxKsyunz
approved these changes
Dec 15, 2022
MaxKsyunz
left a comment
There was a problem hiding this comment.
I'd make it clear in the title that only DESCRIBE statement is affected.
LIKE clauseLIKE clause in DESCRIBE statement
6 tasks
andy-k-improving
pushed a commit
that referenced
this pull request
Nov 16, 2024
* Import h3 library (#154) Made following changes to make it compatible: 1. Rename package from elasticsearch to opensearch.geospatial 2. Update License headers 3. Update build file 4. Update settings to include sub projects * Use Transport Request (#164) Remove usage of deprecated BaseNodeRequest * Update http client package to resolve build failure (#168) (#171) * Introduce H3 min resolution constant (#165) H3 version 1 has 16 resolutions, numbered 0 through 15. Introduced a constant to represent min value, similar to max value. * Add geohex aggregation (#160) This aggregation will use uber's h3 to group coordinates into H3 cell. Created new aggregation type geohex_grid. The precision will be between 0 and 15. This aggreation has default precision as 5, similar to geohash and geotile. Signed-off-by: Vijayan Balasubramanian <balasvij@amazon.com> * Add integration test (#176) Included integration test for geohex_grid. Signed-off-by: Vijayan Balasubramanian <balasvij@amazon.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Yury-Fridlyand yuryf@bitquilltech.com
Description
Update SQL parser to disallow unquoted strings as identifiers wildcards clause.
To test this fix for opensearch-project#650 disable legacy engine first:
Before
With patch, without fix
After
Another queries for test:
and
Notes
As discussed, we should prohibit usage of raw identifies in SQL queries where wildcards are allowed. A user should specify string literal instead (a quoted string with
'or"). Backtick quote`is not accepted.This behavior was copied from legacy engine and it is an erroneous approach.
The root cause of opensearch-project#650 is a
keywordsCanBeIdwhich was in the user query which cased V2 parser to fail and fall back to V1.Issues Resolved
opensearch-project#650
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.